-
Notifications
You must be signed in to change notification settings - Fork 14
Rename vendor error code and update documentation #316
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename vendor error code and update documentation #316
Conversation
This is done to better reflect the purpose of the field, which is to provide a vendor-specific diagnostic code for the error or the warning that the sensor is reporting. The term "diagnostic" is more appropriate than "error" in this context, as it encompasses both errors and warnings. Signed-off-by: Tiyash Basu <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR updates the field name for vendor provided error codes in both sensor and electrical component diagnostics for improved clarity.
- Changed "vendor_error_code" to "vendor_diagnostic_code" in sensors.proto and electrical_components.proto.
- Updated inline comments to clarify error state conditions, with additional notes added to electrical_components.proto regarding unique state members and error population.
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| proto/frequenz/api/common/v1/microgrid/sensors/sensors.proto | Renamed vendor error field and updated comments for clearer diagnostics in SensorDiagnostic messages. |
| proto/frequenz/api/common/v1/microgrid/electrical_components/electrical_components.proto | Renamed vendor error field and revised state error documentation in ElectricalComponentState. |
proto/frequenz/api/common/v1/microgrid/electrical_components/electrical_components.proto
Outdated
Show resolved
Hide resolved
2f5b96a to
88a4907
Compare
florian-wagner-frequenz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, although I am not sure of the impact that the name change might have on the API (how long did this field exist, is anyone using it already?)
proto/frequenz/api/common/v1/microgrid/electrical_components/electrical_components.proto
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but please check the comments by @florian-wagner-frequenz .
Signed-off-by: Tiyash Basu <[email protected]>
88a4907 to
7912d10
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR renames the vendor error code field to vendor diagnostic code and updates the related documentation in the proto files to clarify that list fields are treated as sets (i.e., no duplicates) and to detail behavior when in an error state.
- Renames "vendor_error_code" to "vendor_diagnostic_code" in both sensors.proto and electrical_components.proto.
- Updates documentation comments for list fields (states, warnings, errors) to explicitly state uniqueness and error state behavior.
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| proto/frequenz/api/common/v1/microgrid/sensors/sensors.proto | Renamed vendor error field and refined comments for list uniqueness and error warning handling. |
| proto/frequenz/api/common/v1/microgrid/electrical_components/electrical_components.proto | Renamed vendor error field and updated comments to clarify uniqueness and error state details in component states. |
thomas-nicolai-frequenz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
No description provided.